Amiga Format CD 41

home *** CD-ROM | disk | FTP | other *** search

/ Amiga Format CD 41 / Amiga Format CD41 (1999-06)(Future Publishing)(GB)[!][issue 1999-07].iso / -seriously_amiga- / comms / other / dlg_1_27 / docs / changes.txt next >

Wrap

Text File | 1999-04-19 | 46KB | 901 lines

Changes for DLG V1.27 AreaEd o New module. This is a complete replacement for DLG:MsgAreas and DLG:FileAreas all in one. It is launched differently depending on whether you wish to edit file or message areas. It automatically works with templates generated with AreaTemplate, making area creation a BREEZE. Just a few keystrokes and BOOM, you're done. AreaTemplate o New module. Gives the sysop the ability to create and administer file and message area TEMPLATES. Use these templates with the file and message area editors to quickly create several areas without having to retype the same information over and over again. This module is pre-configured in AreaEd's menu. CompileScreen o There was a nasty bug in CompileScreen that nobody was catching -- guess they didn't use it -- but it's fixed, anyway. Changed all file IO to dos-pure and added some error checking. DLGRexx.library o Added this library to provide an ARexx interface to many dlg.library functions. In this release, only the port-specific functions (LockPort, FreePort, etc) are implemented. Message System o Added a new config directory: DLGConfig:Fido . This directory will eventually be the home of ALL fidonet configs. o Added a new config file: DLGConfig:Fido/Domains. This file tells DLG what your default address is, and what your default address is for each domain that you are in. See docs for more details on how to use it. DLGNet o DLGNet no longer remaps the INTL kludge if you are sending from one zone to another. This will be changed in the near future to allow DLGNet to override the kludges if needed, but it will be done observing the restrictions of DLGConfig:Fido/Domains instead of its own rather limited view of the world :-) Mess o Now uses DLGConfig:Fido/Domains to determine the proper FROM address when writing netmail outside of FidoNet. SendMsg o SendMsg was setting the CRASH bit whenever a netmail message was sent, regardless of flags set in the command line. SendMsg changed to assume that the settings on the command line override the settings in fidonet.settings. o Now uses DLGConfig:Fido/Domains to determine the proper FROM address when writing netmail outside of FidoNet. DLGTick o DLGTick now recognizes a new keyword in an area definition - USEADDR. If USEADDR is present, DLGTick will substitute the specified address for your own address. For example, if you are in AmigaNet and hatch a file out as 39:100/101, you'll notice that previous versions would put your default Fido address in its place. Now, you can specify your AmigaNet address and it will be put in place of your Fido address in all cases. The one exception is the SEENBY statement -- your primary address is left in there, but the specified address is also added as well. This gives an extra layer of protection against dupes coming back to haunt you. =========== Implementing Changes ============== 1. Adding AreaEd to your system 2. Using AreaTemplate Seperately 3. Using dlgrexx.library 4. Configuring Domains 5. Configuring DLGTick for multi-domain operation 6. AreaEd Command Line Options 7. AreaTemplate Command Line Options 8. AreaEd Commands 9. Area Parameters 10. AreaTemplate Commands 11. Area Template Parameters 12. Resource Manager Error Codes (for dlgrexx.library) 1. Adding AreaEd to your System AreaEd totally replaces both MsgAreas and FileAreas, the file and message area configuration programs. The installer script should have done everything for you except actually editing your menus to point to the new programs. While it is possible to change the menus blindly, we have no way of knowing if you kept the default settings, so this last step must be performed by you. For the purposes of this procedure, we will assume that you are using the default Sysop menu that was supplied with DLG. You will be using the [C] CONFIGURE MENUS command to edit the SYSOP menu, specifically the [D] DEFINE / EDIT MESSAGE AREAS and [F] FILE AREA DEFINE / EDIT commands. If your sysop menu does not have these entries, we are going to assume that you know what you are doing and can figure out the generalities on your own. :-) From the sysop menu, select [C] to enter the Menu Editor. Select [S] to SELECT the menu to edit and then select the SYSOP menu. You can [L] LIST the menu to verify that you have the right menu. Assuming you do, select [E] to edit an item, then select D to edit the DEFINE / EDIT MESSAGE AREAS item. Item [2] should be set to "DLG:MsgAreas". You will need to change this to "DLG:AreaEd". If you had other command line options (such as -o) for MsgAreas, you should add them for AreaEd as well. Now, select [E] to edit an item, then select F to edit the FILE AREA DEFINE / EDIT item. Item [2] should be set to "DLG:FileAreas". You will need to change this to "DLG:AreaEd -f". If you had other command line options (such as -o) for MsgAreas, you should add them for AreaEd as well. NOTE THE -f COMMAND LINE OPTION -- THIS IS HOW AREAED KNOWS TO EDIT FILE AREAS INSTEAD OF MESSAGE AREAS. Assuming all was done correctly, you are now ready to use the new area editor modules. Later on in this document you will find a short user-guide on how to use them. The program also comes with some pre-defined help files which have also been installed for you. 2. Using AreaTemplate Seperately AreaTemplate is normally called by AreaEd when you tell AreaEd that you want to edit templates ("T" in the default menu). However, if you wish to break it out to a seperate menu, you may. It is configured exactly like AreaEd above, except of course the name of the program is different. 3. Using dlgrexx.library dlgrexx.library is a new addition as of V1.27. It is a shared Arexx function library that is only available to Arexx scripts. C or asm programmers will have no need of it. To use dlgrexx.library in your Arexx scripts, you simply call the functions listed for the library from your script as you would any Arexx function call. Before you can do this, however, you must have the library open. Near the beginning of your code, add the following: if ~show(l, "dlgrexx.library") then do if ~addlib("dlgrexx.library", 0, -30, 0) then do say "Could not load dlgrexx.library." exit(20) end end This should especially be present if you plan on distributing your Arexx programs to other users. A full list of supported commands is included in dlgrexx.doc. 4. Configuring Domains Domains when used in a FidoNet context refer to different networks. FidoNet itself is a domain that encompasses zones 1 through 7. AmigaNet is another domain, this one encompasing zones 39 through 41. Domains are important if you wish to treat different zones as if they were within one network. Previously, DLGMail took care of this for you as long as the domain in question was FidoNet, but it did not for other domains. The Domains configuration file and the code that uses it is a more thorough and flexible solution. If you are not participating in any FidoNet-tech networks, you won't need to configure the Domains file. Everyone else will. In DLGConfig:Fido you will find a sample file called _Domains. Rename or copy this to DLGConfig:Fido/Domains and open it with a text editor. You should see something like this: ;this is a comment DEFAULT 1:202/720.0 ; this is a comment DOMAIN fido Address 1:202/720.0 Zone 1 Zone 2 Zone 3 Zone 4 Zone 5 Zone 6 @Domain DOMAIN amiganet Address 40:405/101.0 Zone 39 Zone 40 Zone 41 @domain DOMAIN podsnet Address 93:9085/1 Zone 93 @domain This example config file contains descriptors for three domains. You will need at least one domain to be configured. The following keywords are used in the Domains file: ; Comments are preceded by a semicolon. A comment may start anywhere on a line -- everything following it on that line is ignored. DEFAULT The DEFAULT keyword indicates that what follows is your default address. If a domain is not matched by the program using this file, it will use the default address for mail that is originating on your system. DOMAIN Starts a DOMAIN block. Following this keyword is a mnemonic that indicates what domain you are defining. This information will not be shared with other systems, so you can name it whatever you want as long as you use it consistently throughout your system. Case is not important. @DOMAIN Ends a DOMAIN block. ADDRESS Only valid within a DOMAIN block. For the domain in question, this will be the address that your system is known by. ZONE Only valid within a DOMAIN block. You may have as many ZONE lines as you desire for a DOMAIN. Each ZONE keyword is followed by the number of a zone that is contained within the domain in question. 5. Configuring DLGTick for Multi-domain Operation DLGTick in this release will allow use in other than your default domain as well as gate across domain boundaries. For this to work, you must add the UASEADDR keyword. USEADDR must be added within an AREA block and tells DLGTick that for that area, your address is what follows the USEADDR keyword. Example: AREA Z40Amiga DESC Zone 40 AmigaNet Admin PURGE REPLACE LocalArea 74 TO 40:402/101.0 H TO 40:711/15.0 H TO 40:800/765.0 H USEADDR 40:405/101 ANNOUNCE MULTI 494 ANNOUNCE MULTI 495 ANNOUNCE MULTI 496 In this example, I am using my AmigaNet address and want it to appear in the SEENBY lines of the resultant TIC file. 6. AreaEd Command Line Options AreaEd has the following template: AreaEd [-s <stack>] [-m <menu>] [-f] [-o] Meaning: -s <stack> Tells AreaEd to pre-load a command stack that will be executed when the user enters the program. -m <menu> Tells AreaEd to use the indicated menu config instead of AREAED_MAIN. -f Tells AreaEd that it will be editing file areas. If left out, AreaEd will edit message areas. -o Tells AreaEd to launch in OVERLAY mode, where the launching program will stay resident in memory and that program will resume when AreaEd exits. By default, AreaEd is launched in CHAIN mode and automatically re-loads DLG:Menu at the menu you launched AreaEd from. 6. AreaTemplate Command Line Options AreaTemplate has the following template: AreaTemplate [-s <stack>] [-m <menu>] [-f] [-o] Meaning: -s <stack> Tells AreaTemplate to pre-load a command stack that will be executed when the user enters the program. -m <menu> Tells AreaTemplate to use the indicated menu config instead of ATEMP_MAIN. -f Tells AreaTemplate that it will be editing file area templates. If left out, AreaTemplate will edit message area templates. -o Tells AreaTemplate to launch in OVERLAY mode, where the launching program will stay resident in memory and that program will resume when AreaTemplate exits. By default, AreaTemplate is launched in CHAIN mode and automatically re-loads DLG:Menu at the menu you launched AreaTemplate from. AreaEd launches AreaTemplate in OVERLAY mode so that you can return directly back to AreaEd when you are done. 7. AreaEd Commands Available Functions Function Builtin Name Purpose ======== ============ ================================================== Add Area AreaEd_New Takes you through the process of adding a new file or message area. If you have previously created templates, you may use those templates to create the area when prompted. Once an area is created, you are presented with the option to further edit it before committing to saving it. Edit Area AreaEd_Edit Presents you with a menu of parameters that you can edit as needed. See Area Parameters for details) List Areas AreaEd_List Presents you with a list of valid file or message areas. Delete Area AreaEd_Delete Delete an existing file or message area. The area parameters are removed from the BBS list, the area is purged from all users' newscan lists, and the area's directory is deleted from FILE: or MSG:. Alt file paths are NOT deleted. There is no undo for this function!! Move Area AreaEd_Move "Move" (renumber) an existing area to a new number. This operation changes the area definition in the BBS list, changes the number in all users' newscan lists, and renames the area's directory in MSG: or FILE:. At this time, the alt file path is NOT renamed, though you can change that parameter in the area definition. Templates AreaEd_Temp Enter the Template Editor Menu. Exit Menu AreaEd_Exit Leave the Area Editor and return to the previous (assumed to be SYSOP) menu. Help Help Display online help for a command key that you will be asked to choose. Re-Display DisplayMenu Clears screen and re-draws the menu. This is usually only useful if you are (1) online and have suffered line noise, or (2) if you are in Expert or Intermediate help mode and wish to see the full text of the menu. 9. Area Parameters Key M|F Parameter Notes === === =================== ================================================ 1 M F Auto-Access If this flag is set, you will have the option to automatically add the new area to the users' new-scan list. When you un-set this parameter, the auto-access levels are reset to 1 and 1 and all users are purged from of the area. 2 M F Auto-Access Level If the auto-access flag is set, you have the ability to set or change what level of user is automatically included in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. 3 M F Write Access (M) Upload Access (F) This controls the level of user that is allowed to write (upload) to the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. 4 M F Kill Access This controls the level of user that is allowed to kill messages or files in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only kill messages or files that they themselves wrote / uploaded on your BBS, unless they have sysop (usually 255) access. You need not worry about deranged users deleting messages or files all over the place. 5 M F Forward Access (M) Download Access (F) This controls the level of user that is allowed to forward (download) messages (files) from the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only forward messages to areas on the BBS that they have access to unless they have sysop (usually 255) access. 6 M F Copy/Move Access (M) Transfer Access (F) This controls the level of user that is allowed to copy or move (transfer) messages (files) from the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only copy/move (forward) to areas on the BBS that they have access to unless they have sysop (usually 255) access. 7 M Edit Access This controls the level of user that is allowed to edit messages in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only edit what they themselves wrote on your BBS, unless they have sysop (usually 255) access. 8 M F Sysop Access This controls the level of user that is allowed to perform Sysop functions in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. You should be very careful changing this to anything other than 255! Users with Sysop access can do any of the above actions! 9 M Echo Area This flag indicates that the message area will be hosting Echomail from a fidonet-tech network. This flag cancels the Netmail and Newsgroup flags. 10 M Hide Seen-Bys This flag indicates that messages displayed in this area will not show the "Seen-By Kludge" lines in the message. While this information is useful for a sysop, it is of little use to most other people. This flag is only available for Echomail areas. Defaults to YES. 11 M Origin Line Each message you write in an Echomail area must contain an Origin Line. Normally, DLG uses the default origin line defined in the FidoNet Settings Editor. However, you may wish to create a different origin line for different echo types. Additionally, if the echo belongs to a network other than your default network (domain), you must define the origin line AND include your address at the end of the line within parenthesis, e.g. The Techno-Mages' Guild * 613.619.1429 (40:405/101) This setting is only available for Echomail areas. Defaults to the system default. 12 M Netmail Area This flag indicates that the message area will be hosting Netmail from a fidonet-tech network. This flag cancels the Echomail and Newsgroup flags. Note that while you may define as many netmail areas as you wish, DLGMail only recognizes one netmail area per system. 13 M Newsgroup This flag indicates that the message area will be hosting a newsgroup from a UUCP network. This flag cancels the Echomail and Netmail flags. 14 M Newsgroup Name This parameter indicates which newsgroup is being imported into this message area. If you set the Newsgroup flag above, you must enter something in this field. The editor will not let you exit until you do so. 15 M F Use Handles This flag indicates that messages posted in the message area will be tagged with the users' aliases (handles) rather than thier real names. You should be careful with this flag, as many networked message areas (especially fido-tech) do not allow aliases in echos. Defaults to NO. 16 M F Use Signatures This flag indicates that posts in the area will be tagged with the users' signature. DLG offers three types of signatures for message areas: normal (the default), FidoNet (used in Echo areas), and UUCP (used in newsgroups). There is also a special signature for file areas. If one of the latter does not exist, the default signature will be used. If that does not exist, no signature will be appended. 17 M F Translator A Translator is an external program that changes the text in some way. In the past, DLG has shipped with programs such as Jive or kraut that gave mock accents (the latter provided a mock German twist) to the message. Digerati Dreams has discontinued these programs for personal reasons. However, the ability to use such programs is still in place. If you wish, you may consult the three batch files Spare1.batch, Spare2.batch, and Spare3.batch for hints on how to use translator files. 18 F File Requestable This flag indicates that files in the area area are available for FidoNet File REQuests (FREQs) from other BBSs. You should never place sensitive files in file requestable areas. 19 F Copy before Download This flag indicates that files should be copied to a temporary directory before they are downloaded. This is most useful for BBSs that offer more than 1 CD on a "turntable" system. Because of the multitasking nature of the Amiga, it is conceivable that users on different lines might be requesting files from different CDs at the same time, causing excessive wear and tear on the changer (and the sysop's nerves!) 20 F Validate Uploads This flag indicates that files uploaded to the area must be validated before they can be made available to users or for FREQing. You will be alerted to unvalidated files next time that you log on the BBS. 21 M F Message Capacity (M) Validation Area (F) Message Areas: This defines how many messages are to be kept in the message area. When more than that number of messages is added to the area (user writing message, imported message), the lowest number message will be deleted until the number of messages is equal to this number. Any number between 10 and 9000 may be entered. Defaults to 100. File Areas: If the Validate Uploads flag is set, this number will indicate a file area to copy the file to while it is awaiting validation. Not to worry, when the file is validated it will be returned to whence it came. You do not have to set an area here, as the file can be held right where it is if you wish. 22 M Renumber Trigger When the message number of the highest message in an area exceeds this number, the message area will be renumbered. To cut down on system drag, this only occurs when you, the sysop, run the Renumber utility. This number cannot be lower than the capacity of the area. Defaults to 500. Cannot be more than 9999. 23 M Character Set This defines a character set to use to translate messages to another format, such as Norwegien character sets or Macintosh 7-bit. You may only select from a list of installed character sets. Defaults to 0 (PORT DEFAULT). 24 F Alt File Path Files are normally stored in FILE:<Area>/, but you may choose an alternate directory to store them in; this is especially usueful for spreading the load over several drives or partitions. If nothing is set here, the default file path is used. You may enter a path up to 18 characters in length for the alt path. If the specified directory does not exist, it will be created. 25 M F Edit EnterArea.Txt If a file called EnterArea.Txt exists in the message or file area's directory, it will be displayed whenever a user enters the area. You may edit the file on the spot using this command. 26 M F Delete EnterArea.Txt If a file called EnterArea.Txt exists in the message or file area's directory, it can be deleted on the spot using this command. 27 M Edit EchoArea.Txt If a file called EchoArea.Txt exists in a message area's directory, AND that area is an echo area, it will be displayed whenever a user posts to the area. You may edit the file on the spot using this command. 28 M Delete EchoArea.Txt If a file called EchoArea.Txt exists in the message area's directory, it can be deleted on the spot using this command. 29 F Edit UploadFile.txt If a file called UploadFile.Txt exists in a file area's directory, it will be displayed whenever a user uploads to the area. You may edit the file on the spot using this command. 30 F Del UploadFile.Txt If a file called UploadFile.Txt exists in the file area's directory, it can be deleted on the spot using this command. 31 M Edit Screen.dat If a file called Screen.dat exists in a message area's directory, messages written in that area will be screened for words of your choosing, and those words replaced with words also of your choosing. This command will allow you to edit it on the spot. See Editing Screen.dat for details on how this works. This command also compiles the generated file for you. 32 M Delete Screen.dat If a file called Screen.dat exists in the message area's directory, it can be deleted on the spot using this command. 33 M F Apply Template Using this powerful command, you can "blast" all the current settings for an area and apply a set of parameters from a template. Once the template is applied, you can edit it further if needed. 10. AreaTemplate Functions Function Purpose ==================== ======================================================== List Templates Shows a list of all applicable templates (file or message) Create Templates Takes you through the process of creating a new template from scratch (see Template Parameters for details) Edit Template Make changes to an already-existing template. (see Template Parameters for details) Copy Template Copy an existing template over to a new one, which you may then edit. Rename Template Rename an existing template. Delete Template Delete one of your existing templates. Exit Template Menu Leave the Template Editor and return to the previous menu. Help Display online help for a command key that you will be asked to choose. Re-Display Clears screen and re-draws the menu. This is usually only useful if you are (1) online and have suffered line noise, or (2) if you are in Expert or Intermediate help mode and wish to see the full text of the menu. 11. Area Template Paramemters Key M|F Parameter Notes === === =================== ================================================ 1 M F Auto-Access If this flag is set, you will have the option to automatically add the new area to the users' new-scan list. When you un-set this parameter, the auto-access levels are reset to 1 and 1 and all users are purged from of the area. 2 M F Auto-Access Level If the auto-access flag is set, you have the ability to set or change what level of user is automatically included in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. 3 M F Write Access (M) Upload Access (F) This controls the level of user that is allowed to write (upload) to the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. 4 M F Kill Access This controls the level of user that is allowed to kill messages or files in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only kill messages or files that they themselves wrote / uploaded on your BBS, unless they have sysop (usually 255) access. You need not worry about deranged users deleting messages or files all over the place. 5 M F Forward Access (M) Download Access (F) This controls the level of user that is allowed to forward (download) messages (files) from the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only forward messages to areas on the BBS that they have access to unless they have sysop (usually 255) access. 6 M F Copy/Move Access (M) Transfer Access (F) This controls the level of user that is allowed to copy or move (transfer) messages (files) from the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only copy/move (forward) to areas on the BBS that they have access to unless they have sysop (usually 255) access. 7 M Edit Access This controls the level of user that is allowed to edit messages in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. NOTE: Users can only edit what they themselves wrote on your BBS, unless they have sysop (usually 255) access. 8 M F Sysop Access This controls the level of user that is allowed to perform Sysop functions in the area. Must be between 1 and 255, and the upper limit cannot be lower than the lower limit. You should be very careful changing this to anything other than 255! Users with Sysop access can do any of the above actions! 9 M Echo Area This flag indicates that the message area will be hosting Echomail from a fidonet-tech network. This flag cancels the Netmail and Newsgroup flags. 10 M Hide Seen-Bys This flag indicates that messages displayed in this area will not show the "Seen-By Kludge" lines in the message. While this information is useful for a sysop, it is of little use to most other people. This flag is only available for Echomail areas. Defaults to YES. 11 M Origin Line Each message you write in an Echomail area must contain an Origin Line. Normally, DLG uses the default origin line defined in the FidoNet Settings Editor. However, you may wish to create a different origin line for different echo types. Additionally, if the echo belongs to a network other than your default network (domain), you must define the origin line AND include your address at the end of the line within parenthesis, e.g. The Techno-Mages' Guild * 613.619.1429 (40:405/101) This setting is only available for Echomail areas. Defaults to the system default. 12 M Netmail Area This flag indicates that the message area will be hosting Netmail from a fidonet-tech network. This flag cancels the Echomail and Newsgroup flags. Note that while you may define as many netmail areas as you wish, DLGMail only recognizes one netmail area per system. 13 M Newsgroup This flag indicates that the message area will be hosting a newsgroup from a UUCP network. This flag cancels the Echomail and Netmail flags. 15 M F Use Handles This flag indicates that messages posted in the message area will be tagged with the users' aliases (handles) rather than thier real names. You should be careful with this flag, as many networked message areas (especially fido-tech) do not allow aliases in echos. Defaults to NO. 16 M F Use Signatures This flag indicates that posts in the area will be tagged with the users' signature. DLG offers three types of signatures for message areas: normal (the default), FidoNet (used in Echo areas), and UUCP (used in newsgroups). There is also a special signature for file areas. If one of the latter does not exist, the default signature will be used. If that does not exist, no signature will be appended. 17 M F Translator A Translator is an external program that changes the text in some way. In the past, DLG has shipped with programs such as Jive or kraut that gave mock accents (the latter provided a mock German twist) to the message. Digerati Dreams has discontinued these programs for personal reasons. However, the ability to use such programs is still in place. If you wish, you may consult the three batch files Spare1.batch, Spare2.batch, and Spare3.batch for hints on how to use translator files. 18 F File Requestable This flag indicates that files in the area area are available for FidoNet File REQuests (FREQs) from other BBSs. You should never place sensitive files in file requestable areas. 19 F Copy before Download This flag indicates that files should be copied to a temporary directory before they are downloaded. This is most useful for BBSs that offer more than 1 CD on a "turntable" system. Because of the multitasking nature of the Amiga, it is conceivable that users on different lines might be requesting files from different CDs at the same time, causing excessive wear and tear on the changer (and the sysop's nerves!) 20 F Validate Uploads This flag indicates that files uploaded to the area must be validated before they can be made available to users or for FREQing. You will be alerted to unvalidated files next time that you log on the BBS. 21 M F Message Capacity (M) Validation Area (F) Message Areas: This defines how many messages are to be kept in the message area. When more than that number of messages is added to the area (user writing message, imported message), the lowest number message will be deleted until the number of messages is equal to this number. Any number between 10 and 9000 may be entered. Defaults to 100. File Areas: If the Validate Uploads flag is set, this number will indicate a file area to copy the file to while it is awaiting validation. Not to worry, when the file is validated it will be returned to whence it came. You do not have to set an area here, as the file can be held right where it is if you wish. 22 M Renumber Trigger When the message number of the highest message in an area exceeds this number, the message area will be renumbered. To cut down on system drag, this only occurs when you, the sysop, run the Renumber utility. This number cannot be lower than the capacity of the area. Defaults to 500. Cannot be more than 9999. 23 M Character Set This defines a character set to use to translate messages to another format, such as Norwegien character sets or Macintosh 7-bit. You may only select from a list of installed character sets. Defaults to 0 (PORT DEFAULT). 12. Resource Manager Error Codes These error codes will be of most use to programmers, including those using Arexx. The DLG shell commands for resource management do not return these codes, but "filter" them for you and attempt to display meaningful error messages instead. Code Meaning Applicability Notes ==== ====================== ============= ================================ 0 No error All -1 Bad Message Type All Only send one of the supported message types listed in dlg/resman.h -2 Port already active Ports Don't activate the same port twice. -3 Port not active Ports Deactivation and locking requires an active port. -4 Resource not locked All You'll see this if you used the wrong password or if you're going for an "immediate" lock which fails. -5 ResMan not active All You'll get this if DLG's resource manager, ResMan, is not running. This probably means you don't have DLG running, either. -6 Out of Memory All -7 Area in Use Areas You'll see this if you are attempting to get an exclusive lock on a message or file area, but someone's still in it. Always count up the users in an area before locking it. -8 Bad Area Number Areas You'll see this if you are attempting to get a lock on a message or file area that does not exist. -9 Area Empty Areas This tells you that an area has no users in it. -10 Language does not exist Language The requested language does not exist for the module specified (if specified). -11 Nonexistant resource All The requested resource does not exist. -12 Resource in use All -13 Can't load menu Menu The specified menu cannot be locked. It might be in use. It might not exist.